Comments
-
FYI - for anyone who had this issue.. the 12.4.3.266 connect tunnel client seems to have much better auto-reconnect logic as stated in the release notes. It has done well in our testing and we will roll out to all end users this Saturday 4/20/24 and update with our experience. Here is the update mentioned in the release…
-
FYI - for anyone who had this issue.. the 12.4.3.266 connect tunnel client seems to have much better auto-reconnect logic as stated in the release notes. It has done well in our testing and we will roll out to all end users this Saturday 4/20/24 and update with our experience. Here is the update mentioned in the release…
-
I see that 12.4.3 has been released. I will review and update our instance shortly and respond back.
-
Can anyone provide details on this 12.4.2 client update - it may be related to my users' issues. SMA1000-6063 : DeviceVPN user disconnected and reconnected, users were unable to access the resources until reboot
-
@vkrtandra Yes - let me know the best way forward. What level of logs do I need? is debug, and then export logs from the connect tunnel dialog sufficient? It will be difficult as many of our users are used to just using our "refresh vpn" script when this sort of thing happens and I don't have an easy way to enable debug…
-
I have gotten this working (I can call the API and get a result) - I think the problem was the format of my JSON requests but I have tried and abandoned many snippets of powershell along the way. I used IONinja to monitor the pipe during normal operations and saw that the JSON request does not need anything pre-pended to…
-
this (see image below) also happens which was why we originally created the "Refresh VPN" utility. Support just wants logs. I want a programmer to look at the dialog and fix the issue. If the connection type has fallen back to Device VPN, then the connect button should never be greyed out. The re-connect automation of the…
-
This answer feels like I cannot really achieve an "Always On" VPN using the Connect Tunnel Device/User mode. Years back we used an SMA 100 series with NetExtender and had a great always on configuration (I think it was based on the old RAS APIs). The SMA 1000 series with Connect Tunnel is so much better in many ways, but…
-
I am still not seeing anything in the callback. I may need another example showing how to build and submit the JSON request The key two things I should need to do are: 1 - properly format the JSON request - (see code below) 2 - properly submit the JSON request to the SnwlConnect-{Name of the user account} named pipe Here…
-
Thank you! I will try this in the morning. I appreciate the response.
-
VKRTandra - I just saw your comment in the other thread with a sample PS script on the API. Thank you! i will play with this tomorrow.
-
Thank you for the reply! re: can you please confirm if the failure to reconnect User VPN is due to expired session ID? Or have you come across scenarios where client failed to reconnect even when user session ID is valid? I am struggling to understand the question. I don't believe that have never seen "a failure to…
-
I guess another question would be: How many SMA 1000 series users are using the Device VPN / UserVPN model? we use it for our "Always On" VPN When the machine boots and gets network the Connect Tunnel client connects in Device VPN mode using the laptop's machine account credentials and establishes a "Device VPN"…